Managing the sharing of common library packages with subscribers

ABSTRACT

A method for securely sharing a common software package includes storing, within a database, a set of software packages associated with a first namespace, then storing, within the database, a common software package associated with the set of software packages. The common software package is obfuscated and includes an access modifier. A request to install a first software package selected from the set of software packages associated with the namespace is received by a subscriber. In response to the request from the subscriber, the system installs the first software package and the common software package in accordance with the access modifier.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. application Ser. No.15/873,587, filed Jan. 17, 2018, which is incorporated herein byreference in its entirety.

TECHNICAL FIELD

Embodiments of the subject matter described herein relate generally tothe installation and sharing of software code. More particularly,embodiments of the subject matter relate to sharing common librarypackages with subscribers in such a way that the actual code is notexposed to these subscribers.

BACKGROUND

Protecting proprietary information and intellectual property such assource code software is very important to organizations involved insoftware development and management. However, it is often important fordevelopers and users (e.g., partners within a particular organization)to develop and share common library packages of the type that might beused by multiple applications and by multiple subscribers.

Accordingly, it is desirable to provide improved systems and methods forsharing common library packages with subscribers in such a way thatthose subscribers cannot access the software code itself. Furthermore,other desirable features and characteristics will become apparent fromthe subsequent detailed description and the appended claims, taken inconjunction with the accompanying drawings and the foregoing technicalfield and background.

BRIEF DESCRIPTION OF THE DRAWINGS

A more complete understanding of the subject matter may be derived byreferring to the detailed description and claims when considered inconjunction with the following figures, wherein like reference numbersrefer to similar elements throughout the figures.

FIG. 1 is a block diagram showing an exemplary embodiment of a systemfor sharing common library packages;

FIG. 2 is a flow chart of an exemplary embodiment of a method forallowing an ISV to access hidden proprietary software code; and

FIG. 3 is a schematic block diagram of an exemplary multi-tenantcomputing environment.

DETAILED DESCRIPTION

A method for securely sharing a common software package includesstoring, within a database, a set of software packages associated with afirst namespace, then storing, within the database, a common softwarepackage associated with the set of software packages. The commonsoftware package is obfuscated and includes an access modifier. Arequest to install a first software package selected from the set ofsoftware packages associated with the namespace is received from asubscriber. In response to the request from the subscriber, the systeminstalls the first software package and the common software package inaccordance with the access modifier. In this way, a common softwarelibrary or package can be distributed to a subscriber without allowingthe subscriber visibility to the software code itself.

A database system in accordance with one embodiment includes a processorin communication with a memory element that has computer executableinstructions stored thereon. The instructions are configurable to beexecuted by the processor to cause the database system to: store, withina database, a set of software packages associated with a firstnamespace; store, within the database, a common software packageassociated with the set of software packages, the common softwarepackage being obfuscated and including an access modifier; receiving,from a subscriber, a request to install a first software packageselected from the set of software packages associated with thenamespace; and in response to the request from the subscriber,installing the first software package and the common software package inaccordance with the access modifier.

Turning now to FIG. 1, a block diagram showing an exemplary embodimentof a system 100 includes a database or datastore 101, within whichvarious organizations or “orgs” 110, 130 are defined, as discussed infurther detail below. One or more “partners” 111 have access to or areotherwise associated with organization 110, while a subscriber 131(e.g., an individual, partnership, corporation, etc.) is associated withorganization 130. One or more application packages 120, 121, 122, 123are developed (e.g., by partners 111) within a common namespace 115.Subscriber 131 will generally also be associated with a separatenamespace 135, as shown.

In some embodiments, a namespace (e.g., 115 and 135) is a globallyunique string across production instances (as depicted in themulti-tenant architecture described below). Partners may be expected toreserve a particular namespace using an existing mechanism providedwithin the hosting system.

As shown, namespace 115 includes a common library package 120 (alsoreferred to as a “utility package” or “common package service”), whichincludes software code that can be used by multiple application packages121, 122, 123. That is, rather than replicating certain functionalitywithin each application package 121-123, common library package 120provides such functionality, and can be installed once by a subscriber131 and used by each of the associated application packages 121-123.Common library package 120 may provide a wide range of functionality,for example, locationing services (GPS, WiFi, etc.), networkingservices, sensor interfaces, common user interface components, and thelike.

In accordance with various embodiments, when an application package(e.g., 121) is installed by a subscriber 131 (as shown, within namespace135), the associated common library package 120 is also installed,either transparently or with explicit permission of subscriber 131. Insuch cases, the installation of subsequent packages (e.g., packages 122and 123) would typically include determining whether the required commonlibrary package 120 has already been installed within namespace 135. Ifso, then only the application package itself is installed. If not,installation of the common library package 120 takes place using anyconvenient method.

In accordance with various embodiments, common library package 120 isobfuscated. As used herein, the term “obfuscated” means that the code(e.g., source code) is either unviewable by a user or is rendered into asubstantially non-human-readable form. This obfuscation may beaccomplished in a variety of ways. In some embodiments, for example, atext representation of a global signature for the code is returned(i.e., visible by a user), but the contents are not. The term“signature” (or “method signature”) as used herein refers to aspecification of the input and output of a function or method. Suchsignatures might include, for example, parameters and their types,return value(s) and type, exceptions that might be thrown or passedback, and information regarding the availability of a method (e.g.,global, public, static, prototype, etc.)

In accordance with various embodiments, available interfaces for commonlibrary package 120 are provided with a specific, non-global accessmodifier that allows common library package 120 (e.g., its methods,variables, etc.) to be accessed by associated application packages121-123. As used herein, the term “access modifier” refers to asyntactical element, e.g., a keyword, that sets the accessibility ofclasses, methods, and other members of an object in an object-orientedlanguage. Application packages that are not developed within namespace115 and/or are not associated with common library package 120 will nothave access to the interfaces of common library package 120. In someembodiments, a new keyword, annotation, or access modifier is employed.The two examples that follow illustrate, first, an example classutilizing a new keyword as its access modifier, and second, an exampleclass utilizing an annotation as an access modifier.

  // Example of new keyword   namespace public class MyClass {   }   //Example of annotation   @Namespace(“TheNamespace”)   public classMyClass {   }

Turning now to FIG. 2, with continued reference to FIG. 1, a flowchartis shown of an exemplary embodiment of a method 200 for sharing commonlibrary packages (such as 120 in FIG. 1). First, at 201, a set ofapplication packages (e.g., 121-123) are developed and/or stored withina particular namespace (e.g., 115) of database (e.g., 101). Similarly,at 202, a common software package (e.g., 120) associated withapplication packages 121-123 is also stored within namespace 115. Asdiscussed above, common software package 120 is obfuscated and includesan access modifier that allows interface “visibility” only toapplication packages (e.g., 121-123) within the same namespace (115).

Next, at 203, a request is received from a subscriber (e.g. 131) toinstall a particular application package within namespace 115 (e.g.,application package 121). Subsequently, at 204, during installation ofapplication package 121, the associated common library package 120 isinstalled within namespace 135, such that application package 121 hasaccess to its interfaces. If, during the installation process, it isdetermined that common library package 120 already exists withinnamespace 135, then only application package 121 needs to be installed.

FIG. 3 presents, as a non-limiting example, a schematic block diagram ofa multi-tenant computing environment in which the various systems andmethods described herein may be implemented. Specifically, as describedin further detail below, a server may be shared between multipletenants, organizations, or enterprises, referred to herein as amulti-tenant database (or “datastore”).

As used herein, a “tenant” or an “organization” should be understood asreferring to a group of one or more users, subscribers, developers,partners, or the like (typically employees) that share access to commonsubset of the data within the multi-tenant database 330. In this regard,each tenant includes one or more users and/or groups associated with,authorized by, or otherwise belonging to that respective tenant. Statedanother way, each respective user within the multi-tenant system of theservice cloud 300 is associated with, assigned to, or otherwise belongsto a particular one of the plurality of enterprises supported by thesystem of the service cloud 300.

Each enterprise tenant may represent a company, corporate department,business or legal organization, and/or any other entities that maintaindata for sets of users (such as their respective employees or customers)within the multi-tenant system of the service cloud 300. Althoughmultiple tenants may share access to the server 302 and the multi-tenantdatabase 330, the data and services provided from the server 302 to eachtenant can be securely isolated from those provided to other tenants.The multi-tenant architecture therefore allows different sets of usersto share functionality and hardware resources without necessarilysharing any of the data 332 belonging to or otherwise associated withother organizations.

The multi-tenant database 330 may be a repository or other data storagesystem capable of storing and managing the data 332 associated with anynumber of tenant organizations. The multi-tenant database 330 may beimplemented using conventional database server hardware. In variousembodiments, the multi-tenant database 330 shares the processinghardware 304 with the server 302. In other embodiments, the multi-tenantdatabase 330 is implemented using separate physical and/or virtualdatabase server hardware that communicates with the server 302 toperform the various functions described herein.

In an exemplary embodiment, the multi-tenant database 330 includes adatabase management system or other equivalent software capable ofdetermining an optimal query plan for retrieving and providing a subsetof the data 332 to an instance of app (or virtual app) 329 in responseto a query initiated or otherwise provided by an app 329, as describedin greater detail below. The multi-tenant database 330 may alternativelybe referred to herein as an on-demand database, in that the multi-tenantdatabase 330 provides (or is available to provide) data at run-time toon-demand virtual apps 329 generated by the app platform 310 asdescribed in greater detail below.

In practice, the data 332 may be organized and formatted in any mannerto support the app platform 310. In various embodiments, the data 332 issuitably organized into a relatively small number of large data tablesto maintain a semi-amorphous “heap”-type format. The data 332 can thenbe organized as needed for a virtual app 329. In various embodiments,conventional data relationships are established using any number ofpivot tables 334 that establish indexing, uniqueness, relationshipsbetween entities, and/or other aspects of conventional databaseorganization as desired. Further data manipulation and report formattingis generally performed at run-time using a variety of metadataconstructs. Metadata within a universal data directory (UDD) 336, forexample, can be used to describe any number of forms, reports,workflows, user access privileges, business logic and other constructsthat are common to multiple tenants.

Tenant-specific formatting, functions and other constructs may bemaintained as tenant-specific metadata 338 for each tenant, as desired.Rather than forcing the data 332 into an inflexible global structurethat is common to all tenants and apps, the multi-tenant database 330 isorganized to be relatively amorphous, with the pivot tables 334 and themetadata 338 providing additional structure on an as-needed basis. Tothat end, the app platform 310 suitably uses the pivot tables 334 and/orthe metadata 338 to generate “virtual” components of the virtual apps329 to logically obtain, process, and present the relatively amorphousdata from the multi-tenant database 330.

The server 302 may be implemented using one or more actual and/orvirtual computing systems that collectively provide the dynamic type ofapp platform 310 for generating the virtual apps 329. For example, theserver 302 may be implemented using a cluster of actual and/or virtualservers operating in conjunction with each other, typically inassociation with conventional network communications, clustermanagement, load balancing and other features as appropriate. The server302 operates with any sort of processing hardware 307 which isconventional, such as a processor 305, memory 306, input/output features307 and the like. The input/output features 307 generally represent theinterface(s) to networks (e.g., to the network 345, or any other localarea, wide area or other network), mass storage, display devices, dataentry devices and/or the like.

The processor 305 may be implemented using any suitable processingsystem, such as one or more processors, controllers, microprocessors,microcontrollers, processing cores and/or other computing resourcesspread across any number of distributed or integrated systems, includingany number of “cloud-based” or other virtual systems. The memory 306represents any non-transitory short or long term storage or othercomputer-readable media capable of storing programming instructions forexecution on the processor 305, including any sort of random accessmemory (RAM), read only memory (ROM), flash memory, magnetic or opticalmass storage, and/or the like. The computer-executable programminginstructions, when read and executed by the server 302 and/or processors305, cause the server 302 and/or processors 305 to create, generate, orotherwise facilitate the app platform 310 and/or virtual apps 329 andperform one or more additional tasks, operations, functions, and/orprocesses described herein. It should be noted that the memory 306represents one suitable implementation of such computer-readable media,and alternatively or additionally, the server 302 could receive andcooperate with external computer-readable media that is realized as aportable or mobile component or platform, e.g., a portable hard drive, aUSB flash drive, an optical disc, or the like.

Each app 328 is suitably generated at run-time (or on-demand) using acommon type of app platform 310 that securely provides access to thedata 332 in the multi-tenant database 330 for each of the various tenantorganizations subscribing to the service cloud 300. In accordance withone non-limiting example, the service cloud 300 is implemented in theform of an on-demand multi-tenant customer relationship management (CRM)system that can support any number of authenticated users for aplurality of tenants. Mobile tenant devices 340 might include, forexample, tablets, smartphones, wearable Google Glass™, and any othercomputing device.

The app platform 310 is any sort of software app or other dataprocessing engine that generates the virtual apps 329 including appsrelating to arranging graphic elements in user interfaces that providedata and/or services to the tenant devices 340. In a typical embodiment,the app platform 310 gains access to processing resources,communications interface and other features of the processing hardware304 using any sort of conventional or proprietary operating system 308.The virtual apps 329 are typically generated at run-time in response toinput received from the tenant devices 340. For the illustratedembodiment, the app platform 310 includes a bulk data processing engine312, a query generator 314, a search engine 316 that provides textindexing and another search functionality, and a runtime app generator320. Each of these features may be implemented as a separate process orother module, and many equivalent embodiments could include differentand/or additional features, components or other modules as desired.

The runtime app generator 320 dynamically builds and executes thevirtual apps 329 in response to specific requests received from thetenant devices 340. The virtual apps 329 are typically constructed inaccordance with the tenant-specific metadata 338, which describes thetables, reports, interfaces and/or other features of the app 329. Invarious embodiments, each virtual app 329 generates dynamic web contentthat can be served to a browser or another tenant program 342 associatedwith its tenant device 340, as appropriate.

The runtime app generator 320 suitably interacts with the querygenerator 314 to efficiently obtain data 332 from the multi-tenantdatabase 330 as needed in response to input queries initiated orotherwise provided by users of the tenant devices 340. In a typicalembodiment, the query generator 314 considers the identity of the userrequesting a particular function (along with the user's associatedtenant), and then builds and executes queries to the multi-tenantdatabase 330 using system-wide metadata 336, tenant specific metadata,pivot tables 334, and/or any other available resources. The querygenerator 314 in this example therefore maintains security of the commondatabase by ensuring that queries are consistent with access privilegesgranted to the user and/or tenant that initiated the request.

With continued reference to FIG. 3, the bulk data processing engine 312performs bulk processing operations on the data 332 such as uploads ordownloads, updates, online transaction processing, and/or the like. Inmany embodiments, less urgent bulk processing of the data 332 can bescheduled to occur as processing resources become available, therebygiving priority to more urgent data processing by the query generator314, the search engine 316, the virtual apps 329, etc.

In exemplary embodiments, the app platform 310 is utilized to createand/or generate data-driven virtual apps 329 for the tenants that theysupport. Such virtual apps 329 may make use of interface features suchas custom (or tenant-specific) screens 324, standard (or universal)screens 322 or the like. Any number of custom and/or standard objects326 may also be available for integration into tenant-developed virtualapps 329. As used herein, “custom” should be understood as meaning thata respective object or app is tenant-specific (e.g., only available tousers associated with a particular tenant in the multi-tenant system) oruser-specific (e.g., only available to a particular subset of userswithin the multi-tenant system), whereas “standard” or “universal” appsor objects are available across multiple tenants in the multi-tenantsystem.

The data 332 associated with each virtual app 329 is provided to themulti-tenant database 330, as appropriate, and stored until it isrequested or is otherwise needed, along with the metadata 338 thatdescribes the particular features (e.g., reports, tables, functions,objects, fields, formulas, code, etc.) of that particular virtual app329. For example, a virtual app 329 may include several objects 326accessible to a tenant, wherein for each object 326 accessible to thetenant, information pertaining to its object type along with values forvarious fields associated with that respective object type aremaintained as metadata 338 in the multi-tenant database 330. In thisregard, the object type defines the structure (e.g., the formatting,functions and other constructs) of each respective object 326 and thevarious fields associated therewith.

Still referring to FIG. 3, the data and services provided by the server302 can be retrieved using any sort of personal computer, mobiletelephone, tablet or another network-enabled tenant device 340 on thenetwork 345. In an exemplary embodiment, the tenant device 340 includesa display device, such as a monitor, screen, or another conventionalelectronic display capable of graphically presenting data and/orinformation retrieved from the multi-tenant database 330, as describedin greater detail below.

Typically, the user operates a conventional browser app or other tenantprogram 342 executed by the tenant device 340 to contact the server 302via the network 345 using a networking protocol, such as the hypertexttransport protocol (HTTP) or the like. The user typically authenticateshis or her identity to the server 302 to obtain a session identifier(“Session ID”) that identifies the user in subsequent communicationswith the server 302. When the identified user requests access to avirtual app 329, the runtime app generator 320 suitably creates the appat run time based upon the metadata 338, as appropriate. However, if auser chooses to manually upload an updated file (through either the webbased user interface or through an API), it will also be sharedautomatically with all the users/devices that are designated forsharing.

As noted above, the virtual app 329 may contain Java, ActiveX, or othercontent that can be presented using conventional tenant software runningon the tenant device 340; other embodiments may simply provide dynamicweb or other content that can be presented and viewed by the user, asdesired. As described in greater detail below, the query generator 314suitably obtains the requested subsets of data 332 from the multi-tenantdatabase 330 as needed to populate the tables, reports or other featuresof the particular virtual app 329.

Techniques and technologies may be described herein in terms offunctional and/or logical block components, and with reference tosymbolic representations of operations, processing tasks, and functionsthat may be performed by various computing components or devices. Suchoperations, tasks, and functions are sometimes referred to as beingcomputer-executed, computerized, software-implemented, orcomputer-implemented. In practice, one or more processor devices cancarry out the described operations, tasks, and functions by manipulatingelectrical signals representing data bits at memory locations in thesystem memory, as well as other processing of signals. The memorylocations where data bits are maintained are physical locations thathave particular electrical, magnetic, optical, or organic propertiescorresponding to the data bits. It should be appreciated that thevarious block components shown in the figures may be realized by anynumber of hardware, software, and/or firmware components configured toperform the specified functions. For example, an embodiment of a systemor a component may employ various integrated circuit components, e.g.,memory elements, digital signal processing elements, logic elements,look-up tables, or the like, which may carry out a variety of functionsunder the control of one or more microprocessors or other controldevices.

When implemented in software or firmware, various elements of thesystems described herein are essentially the code segments orinstructions that perform the various tasks. The program or codesegments can be stored in a processor-readable medium or transmitted bya computer data signal embodied in a carrier wave over a transmissionmedium or communication path. The “processor-readable medium” or“machine-readable medium” may include any medium that can store ortransfer information. Examples of the processor-readable medium includean electronic circuit, a semiconductor memory device, a ROM, a flashmemory, an erasable ROM (EROM), a floppy diskette, a CD-ROM, an opticaldisk, a hard disk, a fiber optic medium, a radio frequency (RF) link, orthe like. The computer data signal may include any signal that canpropagate over a transmission medium such as electronic networkchannels, optical fibers, air, electromagnetic paths, or RF links. Thecode segments may be downloaded via computer networks such as theInternet, an intranet, a LAN, or the like.

“Node/Port”—As used herein, a “node” means any internal or externalreference point, connection point, junction, signal line, conductiveelement, or the like, at which a given signal, logic level, voltage,data pattern, current, or quantity is present. Furthermore, two or morenodes may be realized by one physical element (and two or more signalscan be multiplexed, modulated, or otherwise distinguished even thoughreceived or output at a common node). As used herein, a “port” means anode that is externally accessible via, for example, a physicalconnector, an input or output pin, a test probe, a bonding pad, or thelike.

“Connected/Coupled”—The following description refers to elements ornodes or features being “connected” or “coupled” together. As usedherein, unless expressly stated otherwise, “coupled” means that oneelement/node/feature is directly or indirectly joined to (or directly orindirectly communicates with) another element/node/feature, and notnecessarily mechanically. Likewise, unless expressly stated otherwise,“connected” means that one element/node/feature is directly joined to(or directly communicates with) another element/node/feature, and notnecessarily mechanically. Thus, although the schematic shown in FIG. 2depicts one exemplary arrangement of elements, additional interveningelements, devices, features, or components may be present in anembodiment of the depicted subject matter.

In addition, certain terminology may also be used in the followingdescription for the purpose of reference only, and thus are not intendedto be limiting. For example, terms such as “upper”, “lower”, “above”,and “below” refer to directions in the drawings to which reference ismade. Terms such as “front”, “back”, “rear”, “side”, “outboard”, and“inboard” describe the orientation and/or location of portions of thecomponent within a consistent but arbitrary frame of reference which ismade clear by reference to the text and the associated drawingsdescribing the component under discussion. Such terminology may includethe words specifically mentioned above, derivatives thereof, and wordsof similar import. Similarly, the terms “first”, “second”, and othersuch numerical terms referring to structures do not imply a sequence ororder unless clearly indicated by the context.

For the sake of brevity, conventional techniques related to signalprocessing, data transmission, signaling, network control, and otherfunctional aspects of the systems (and the individual operatingcomponents of the systems) may not be described in detail herein.Furthermore, the connecting lines shown in the various figures containedherein are intended to represent exemplary functional relationshipsand/or physical couplings between the various elements. It should benoted that many alternative or additional functional relationships orphysical connections may be present in an embodiment of the subjectmatter.

The foregoing detailed description is merely illustrative in nature andis not intended to limit the embodiments of the subject matter or theapplication and uses of such embodiments. As used herein, the word“exemplary” means “serving as an example, instance, or illustration.”Any implementation described herein as exemplary is not necessarily tobe construed as preferred or advantageous over other implementations.Furthermore, there is no intention to be bound by any expressed orimplied theory presented in the preceding technical field, background,or detailed description.

While at least one exemplary embodiment has been presented in theforegoing detailed description, it should be appreciated that a vastnumber of variations exist. It should also be appreciated that theexemplary embodiment or embodiments described herein are not intended tolimit the scope, applicability, or configuration of the claimed subjectmatter in any way. Rather, the foregoing detailed description willprovide those skilled in the art with a convenient road map forimplementing the described embodiment or embodiments. It should beunderstood that various changes can be made in the function andarrangement of elements without departing from the scope defined by theclaims, which includes known equivalents and foreseeable equivalents atthe time of filing this patent application.

What is claimed is:
 1. A method for securely sharing a common software package, comprising: storing, within a database, a set of software packages associated with a namespace wherein the namespace is a globally unique limiter across production instances; storing, within the database, a common software package associated with the set of software packages and the namespace, the common software package including an access modifier; receiving, from a subscriber, a request to install a first software package selected from the set of software packages associated with the namespace; and in response to the request from the subscriber, installing the first software package and the common software package in accordance with the access modifier wherein the common software package is installed transparently to the subscriber and wherein the access modifier allows subscriber visibility to the first software package and restricts subscriber visibility to the common software package.
 2. The method of claim 1, wherein the common software package comprises source code.
 3. The method of claim 2, where the common software package comprises a managed object class.
 4. The method of claim 1, wherein the access modifier is a class annotation.
 5. The method of claim 1, wherein the access modifier is a keyword.
 6. The method of claim 1, wherein the common software package is obfuscated by returning only a global signature for an object within the common software package.
 7. The method of claim 1, wherein the database is multi-tenant database.
 8. A computer readable media having computer-executable instructions stored thereon and configurable to be executed by a processor to perform a method comprising: storing, within a database, a set of software packages associated with a namespace wherein the namespace is a globally unique limiter across production instances; storing, within the database, a common software package associated with the set of software packages and the namespace, the common software package including an access modifier; receiving, from a subscriber, a request to install a first software package selected from the set of software packages associated with the namespace; and in response to the request from the subscriber, installing the first software package and the common software package in accordance with the access modifier wherein the common software package is installed transparently to the subscriber and wherein the access modifier allows subscriber visibility to the first software package and restricts subscriber visibility to the common software package.
 9. The computer readable media of claim 8, wherein the common software package comprises source code.
 10. The computer readable media of claim 8, where the common software package comprises a managed object class.
 11. The computer readable media of claim 8, wherein the access modifier is a class annotation.
 12. The computer readable media of claim 8, wherein the access modifier is a keyword.
 13. The computer readable media of claim 8, wherein the common software package is obfuscated by returning only a global signature for an object within the common software package.
 14. The computer readable media of claim 8, wherein the database is a multitenant database.
 15. A database system comprising a processor in communication with a memory element that has computer-executable instructions stored thereon and configurable to be executed by the processor to cause the database system to: store, within a database, a set of software packages associated with a namespace wherein the namespace is a globally unique limiter across production instances; store, within the database, a common software package associated with the set of software packages and the namespace, the common software package including an access modifier; receiving, from a subscriber, a request to install a first software package selected from the set of software packages associated with the namespace; and in response to the request from the subscriber, installing the first software package and the common software package in accordance with the access modifier wherein the common software package is installed transparently to the subscriber and wherein the access modifier allows subscriber visibility to the first software package and restricts subscriber visibility to the common software package.
 16. The database system of claim 15, wherein the common software package comprises source code.
 17. The database system of claim 16, where the common software package comprises a managed object class.
 18. The database system of claim 15, wherein the access modifier is a class annotation.
 19. The database system of claim 15, wherein the access modifier is a keyword.
 20. The database system of claim 15, wherein the common software package is obfuscated by returning only a global signature for an object within the common software package. 